• interface is the same as for storage reads
• reads are from the init json, rather than key-value store
• pay attention to which types are returned.

The attached zip file

remote_reads_contract_params_tests.zip

contains a set of suggested regression tests, to be used as follows:

• Deploy remote_reads_support.scilla using the init file support_init.json. Remember to change the _this_address entry to the address that the contract is deployed at.
• Deploy remote_reads_test.scilla using the init file test_init.json. Remember to change the _this_address entry to the address that the contract is deployed at, and the entry support_contract_init to the address that the support contract is deployed at.
• Invoke the transitions Test1, Test2, ..., Test18 on the test contract. None of them take any parameters. The expected behavior of all of them is that they terminate without raising a Scilla exception. If they terminate with a Scilla exception, then something has gone wrong in the implementation.

None of the transitions make changes to the contract states, so it should be possible to deploy the contracts once and invoke all the transitions one by one. There is no need to redeploy between each transition invocation.

Note that I have not been able to test the contracts, so it is possible that I have made a mistake when writing them. If you encounter an exception, then the first thing to do is to make sure that the Scilla code actually does what it's supposed to.

This is ancient and is likely never to be merged; closing.